Mounting a smartphone to robotic accessor of automated data storage library

ABSTRACT

According to one embodiment, a computer-implemented method for remotely controlling a capture of images of a data storage library during operation thereof with a bracket on an accessor includes pairing a remote controller to a wireless image capture device that is coupled to a bracket mounted on an accessor, instructing the wireless image capture device to start recording images of the data storage library during operation thereof, including movement of the accessor, thereafter, instructing the wireless image capture device to stop recording images of the data storage library during operation thereof, and instructing the wireless image capture device to save the recorded images to a file.

BACKGROUND

The present invention relates to data storage systems, and moreparticularly, this invention relates to automated data storagelibraries.

Automated data storage libraries are known for providing cost effectivestorage and retrieval of large quantities of data. The data in automateddata storage libraries is typically stored on media of data storagecartridges that are, in turn, stored at storage slots or the like insidethe library in a fashion that renders the media, and its resident data,accessible for physical retrieval. Such data storage cartridges arecommonly termed “removable media.” Data storage cartridge media maycomprise any type of media on which data may be stored and which mayserve as removable media, including but not limited to magnetic media(such as magnetic tape or disks), optical media (such as optical tape ordisks), electronic media (such as PROM, EEPROM, flash PROM,CompactFlash™, Smartmedia™, Memory Stick™, etc.), or other suitablemedia. An example of a data storage cartridge that is widely employed inautomated data storage libraries for mass data storage is a magnetictape cartridge.

In addition to data storage media, automated data storage librariestypically comprise data storage drives that store data to, and/orretrieve data from, the data storage cartridge media. Further, automateddata storage libraries typically comprise I/O stations at which datastorage cartridges are supplied or added to, or removed from, thelibrary. The transport of data storage cartridges between data storageslots, data storage drives, and I/O stations is typically accomplishedby one or more accessors. Such accessors have grippers for physicallyretrieving the selected data storage cartridges from the storage slotswithin the automated data storage library and transporting suchcartridges to the data storage drives by moving, for example, in thehorizontal (X) and vertical (Y) directions.

In an effort to increase storage capacity, deep slot technology allowsfor storage cells that contain more than a single data storagecartridge. Such storage libraries allow for higher density, or morecartridges stored per square foot. In ‘deep slot’ libraries, two or morecartridges may be stored in a multi-cartridge deep slot cell, arrayed inseries, one behind the other, in tiers ranging from a frontmost tier toa rearmost tier.

Automated storage libraries use one or more robotic mechanisms as a partof the accessor to move data storage media back and forth from storageelements or import export elements to data storage drives within thelibrary. Trouble-shooting issues with the accessor and the associatedrobotic mechanisms may be addressed with a method to record images ofthe activity of the accessor robotic components while the accessor isrunning.

SUMMARY

According to one embodiment, a computer-implemented method for remotelycontrolling a capture of images of a data storage library duringoperation thereof with a bracket on an accessor includes pairing aremote controller to a wireless image capture device that is coupled toa bracket mounted on an accessor, instructing the wireless image capturedevice to start recording images of the data storage library duringoperation thereof, including movement of the accessor, thereafter,instructing the wireless image capture device to stop recording imagesof the data storage library during operation thereof, and instructingthe wireless image capture device to save the recorded images to a file.

According to another embodiment, a computer-implemented method forremotely controlling, by a support center, a capture of images of a datastorage library during operation thereof with a wireless image capturedevice located at a customer site includes connecting to the wirelessimage capture device, where the wireless image capture device isconfigured to be controlled remotely by a remote controller located atthe support center. Next, the computer-implemented method includessending an instruction to the data storage library, by the remotecontroller located at the support center, to move an accessor of thedata storage library, sending an instruction to the wireless imagecapture device to start recording images of the data storage libraryduring operation thereof, where the wireless image capture device ismounted in a bracket on the accessor, sending an instruction to the datastorage library to stop moving the accessor, sending an instruction tothe wireless image capture device to stop recording images of the datastorage library, and receiving the recorded images from the wirelessimage capture device.

Other aspects and embodiments of the present invention will becomeapparent from the following detailed description, which, when taken inconjunction with the drawings, illustrate by way of example theprinciples of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of an automated data storage libraryaccording to one embodiment.

FIG. 2 is a perspective view of a storage frame from the data storagelibrary of FIG. 1.

FIG. 3 is a block diagram of an automated data storage library accordingto one embodiment.

FIG. 4 is a block diagram depicting a controller configuration accordingto one embodiment.

FIG. 5A is a front perspective view of a data storage drive according toone embodiment.

FIG. 5B is a rear perspective view of the data storage drive of FIG. 5A.

FIG. 6 is perspective view of a data storage cartridge having a cutawayportion, according to one embodiment.

FIGS. 7A-7B are perspective views of a multi-cartridge deep slot cellaccording to one embodiment.

FIGS. 8A-8D are partial side views of a cartridge blocking mechanismaccording to one embodiment.

FIG. 9 illustrates a tiered data storage system in accordance with oneembodiment.

FIG. 10A is an expanded side view of the robotic accessor of a tapelibrary according to one embodiment.

FIG. 10B is an expanded front view of the robotic accessor of a tapelibrary according to one embodiment.

FIG. 11 is a flowchart of a method according to one embodiment.

FIG. 12 is a flowchart of a method according to one embodiment.

DETAILED DESCRIPTION

The following description is made for the purpose of illustrating thegeneral principles of the present invention and is not meant to limitthe inventive concepts claimed herein. Further, particular featuresdescribed herein can be used in combination with other describedfeatures in each of the various possible combinations and permutations.

Unless otherwise specifically defined herein, all terms are to be giventheir broadest possible interpretation including meanings implied fromthe specification as well as meanings understood by those skilled in theart and/or as defined in dictionaries, treatises, etc.

It must also be noted that, as used in the specification and theappended claims, the singular forms “a,” “an” and “the” include pluralreferents unless otherwise specified.

The following description discloses several preferred embodiments ofdata storage systems, as well as operation and/or component partsthereof. In one general embodiment, an apparatus includes an accessorconfigured to transport data storage cartridges in a libraryenvironment, and a bracket configured to receive a wireless imagecapture device therein, where the bracket is positioned to orient thewireless image capture device to capture images while the accessor istransporting data storage cartridges.

In another general embodiment, a method for mounting a wireless capturedevice to an accessor to capture images of an operation in a datastorage library includes mounting a bracket to the accessor, where theaccessor is configured to transport data storage cartridges in a libraryenvironment, where the bracket is configured to receive a wireless imagecapture device therein. Moreover, the bracket is mounted in a positionto orient the wireless image capture device to capture images while theaccessor is transporting data storage cartridges.

In another general embodiment, a method for capturing an image of anoperation in a data storage library with a bracket on an accessorincludes locating a bracket mounted in a position to orient a wirelessimage capture device on the accessor. The method further includesmounting the wireless image capture device into the bracket wherein anaperture of the bracket is aligned with an aperture of the wirelessimage capture device. The accessor is run while the wireless imagecapture device is recording images of the operation in the data storagelibrary. The recording of the images of the operation by the wirelessimage capture device is stopped, and the wireless image capture deviceis removed from the bracket on the accessor and the recorded images areviewed.

FIGS. 1-2 illustrate an automated data storage library 10 which storesand retrieves data storage cartridges, containing data storage media(not shown), from multi-cartridge deep slot cells 100 and singlecartridge storage slots 16. An example of an automated data storagelibrary which has a similar configuration as that depicted in FIGS. 1-2,and may be implemented with some of the various approaches herein is theIBM 3584 UltraScalable Tape Library. Moreover, it should be noted thatreferences to “data storage media” herein refer to data storagecartridges, and for purposes of the present application, the two termsmay be used synonymously.

The library 10 of FIG. 1 comprises a left hand service bay 13, one ormore storage frames 11, and right hand service bay 14. As will bediscussed in further detail below, a frame may comprise an expansioncomponent of the library. Thus, storage frames may be added or removedto expand or reduce the size and/or functionality of the library.According to different approaches, frames may include additional storageslots, deep slot cells, drives, import/export stations, accessors,operator panels, etc.

FIG. 2 shows an exemplary embodiment of a storage frame 11, which actsas the base frame of the library 10. Moreover, the storage frame 11illustrated in FIG. 2 is contemplated to be a minimum configuration ofthe library 10, for which there is only a single accessor 18 (i.e.,there are no redundant accessors) and no service bay. However, in otherembodiments, a storage frame may include multiple robotic accessorsand/or service bays.

Looking to FIG. 2, the library 10 is arranged for accessing data storagemedia in response to commands from at least one external host system(not shown). The library 10 includes a plurality of storage slots 16 onfront wall 17 and a plurality of multi-cartridge deep slot cells 100 onrear wall 19, both of which may be used for storing data storagecartridges that may contain data storage media. According to oneapproach, the storage slots 16 are configured to store a single datastorage cartridge, and the multi-cartridge deep slot cells 100 areconfigured to store a plurality of data storage cartridges. In apreferred approach, the multi-cartridge deep slot cells may be arrangedin sequential order of tiers from front to rear (e.g., see FIG. 7A).

With continued reference to FIG. 2, the storage frame 11 of the library10 also includes at least one data storage drive 15, e.g., for readingand/or writing data with respect to the data storage media.Additionally, a first accessor 18 may be used to transport data storagemedia between the plurality of storage slots 16, the multi-cartridgedeep slot cells, and/or the data storage drive(s) 15. According tovarious approaches, the data storage drives 15 may be optical diskdrives, magnetic tape drives, or other types of data storage drives asare used to read and/or write data with respect to the data storagemedia.

As illustrated, the storage frame 11 may optionally include an operatorpanel or other user interface, such as a web-based interface, whichallows a user to interact with the library 10. The storage frame 11 mayalso optionally comprise an upper I/O station 24 and/or a lower I/Ostation 25, thereby allowing data storage cartridges to be added (e.g.,inserted) to the library inventory and/or removed from the librarywithout disrupting library operation. Furthermore, the library 10 mayhave one or more storage frames 11, each having storage slots 16,preferably accessible by the first accessor 18.

As described above, the storage frames 11 may be configured withdifferent components depending upon the intended function. Oneconfiguration of storage frame 11 may comprise storage slots 16 and/ormulti-cartridge deep slot cells 100, data storage drive(s) 15, and otheroptional components to store and retrieve data from the data storagecartridges. However, in another approach, a storage frame 11 may includestorage slots 16 and/or multi-cartridge deep slot cells 100 and no othercomponents. The first accessor 18 may have a gripper assembly 20, e.g.,for gripping one or more data storage media, in addition to having a barcode scanner or other reading system, such as a cartridge memory readeror similar system mounted on the gripper assembly 20, to “read”identifying information about the data storage media.

FIG. 3 depicts an automated data storage library 10, in accordance withone embodiment. As an option, the present automated data storage library10 may be implemented in conjunction with features from any otherembodiment listed herein, such as those described with reference to theother FIGS. Of course, however, such automated data storage library 10and others presented herein may be used in various applications and/orin permutations which may or may not be specifically described in theillustrative embodiments listed herein. Further, the automated datastorage library 10 presented herein may be used in any desiredenvironment. Thus FIG. 3 (and the other FIGS.) should be deemed toinclude any and all possible permutations

Referring now to FIG. 3, the automated data storage library 10 asdescribed in reference to FIGS. 1 and 2, is depicted according to oneembodiment. According to a preferred approach, the library 10 may employa controller, e.g., arranged as a distributed system of modules with aplurality of processor nodes.

In one approach, the library is controlled, not by a central controller,but rather, by a distributed control system for receiving logicalcommands and converting the commands to physical movements of theaccessor and gripper, and for operating the drives in accordance withthe desired physical movements. The distributed control system may alsoprovide logistical support, such as responding to host requests forelement status, inventory, library status, etc. The specific commands,the conversion of those commands to physical movements, and theoperation of the drives may be of a type known to those of skill in theart.

While the automated data storage library 10 has been described asemploying a distributed control system, various other approachesdescribed and/or suggested herein may be implemented in automated datastorage libraries regardless of control configuration, such as, but notlimited to, an automated data storage library having one or more librarycontrollers that are not distributed.

Referring still to FIG. 3, the library 10 may have one or more storageframes 11, a left hand service bay 13 and a right hand service bay 14.The left hand service bay 13 is shown with a first accessor 18, where,as discussed above, the first accessor 18 may include a gripper assembly20 and/or a bar code scanner (e.g., reading system) 22 to “read”identifying information about the data storage media depending on thedesired embodiment. Furthermore, the right hand service bay 14 is shownhaving a second accessor 28, which includes a gripper assembly 30 andmay also include a reading system 32 to “read” identifying informationabout the data storage media.

According to one approach, in the event of a failure or otherunavailability of the first accessor 18, or its gripper assembly 20,etc., the second accessor 28 may perform some or all of the functions ofthe first accessor 18. Thus in different approaches, the two accessors18, 28 may share one or more mechanical paths, they may have completelyindependent mechanical paths, or combinations thereof. In one example,the accessors 18, 28 may have a common horizontal rail with independentvertical rails to travel therealong. Moreover, it should be noted thatthe first and second accessors 18, 28 are described as first and secondfor descriptive purposes only and this description is not meant to limiteither accessor to an association with either the left hand service bay13, or the right hand service bay 14.

In an exemplary embodiment which is in no way intended to limit theinvention, the first and second accessors 18, 28 may preferably movetheir grippers in at least two directions, called the horizontal “X”direction and vertical “Y” direction, e.g., to retrieve and grip,deliver and release, load and unload, etc. the data storage cartridge atthe storage slots 16, multi-cartridge deep slot cells 100, data storagedrives 15, etc.

With continued reference to FIG. 3, library 10 receives commands fromone or more host systems 40, 41, 42. The host systems 40, 41, 42, suchas host servers, communicate with the library directly, e.g., on path80, through one or more control ports (not shown), or through one ormore data storage drives 15 on paths 81, 82. Thus, in differentapproaches, the host systems 40, 41, 42 may provide commands to accessparticular data storage cartridges and move the cartridges, for example,between the storage slots 16 and the data storage drives 15. Thecommands are typically logical commands identifying the cartridges orcartridge media, and/or logical locations for accessing the media.Furthermore, it should be noted that the terms “commands” and “workrequests” are used interchangeably herein to refer to suchcommunications from the host system 40, 41, 42 to the library 10 as areintended to result in accessing particular data storage media within thelibrary 10 depending on the desired approach.

According to one embodiment, the library 10 may be controlled by alibrary controller. Moreover, in various approaches, the librarycontroller may include a distributed control system receiving thelogical commands from hosts, determining the required actions, and/orconverting the actions to physical movements of the first and/or secondaccessor 18, 28. In another approach, the distributed control system mayhave a plurality of processor nodes, each having one or more computerprocessors. According to one example of a distributed control system, acommunication processor node 50 may be located in a storage frame 11.The communication processor node provides a communication link forreceiving the host commands, either directly or through the drives 15,via at least one external interface, e.g., coupled to line 80.

Still referring to FIG. 3, the communication processor node 50 mayadditionally provide a communication link 70 for communicating with thedata storage drives 15. As illustrated, the communication processor node50 may preferably be located in the storage frame 11, e.g., close to thedata storage drives 15. Furthermore, one or more additional workprocessor nodes may be provided to form an exemplary distributedprocessor system, which may comprise, e.g., a work processor node 52located at first accessor 18, and that is coupled to the communicationprocessor node 50 via a network 60, 157. According to differentapproaches, each work processor node may respond to received commandsthat are broadcast thereto from any communication processor node, andthe work processor nodes may also direct the operation of the accessors,e.g., providing move commands. An XY processor node 55 may be providedand may be located at an XY system of first accessor 18. As illustrated,the XY processor node 55 is coupled to the network 60, 157, and isresponsive to the move commands, operating the XY system to position thegripper assembly 20.

Also, an operator panel processor node 59 may be provided at theoptional operator panel for providing an interface for communicatingbetween the operator panel and the communication processor node 50, thework processor nodes 52, 252, and the XY processor nodes 55, 255.

A network 60, for example comprising a common bus, is provided, couplingthe various processor nodes. The network may comprise a robust wiringnetwork, such as the commercially available Controller Area Network(CAN) bus system, which is a multi-drop network, having a standardaccess protocol and wiring standards, for example, as defined by CiA,the CAN in Automation Association, Am Weich Selgarten 26, D-91058Erlangen, Germany. Other networks, such as Ethernet, or a wirelessnetwork system, such as RF or infrared, may be employed in the libraryas is known to those of skill in the art. In addition, multipleindependent networks may also be used to couple the various processornodes.

As illustrated in FIG. 3, the communication processor node 50 is coupledto each of the data storage drives 15 of a storage frame 11, via lines70, and are thereby communicating with the drives 15 and with hostsystems 40, 41, 42. Alternatively, the host systems 40, 41, 42 may bedirectly coupled to the communication processor node 50, at input 80 forexample, or to control port devices (not shown) which connect thelibrary to the host system(s) with a library interface similar to thedrive/library interface. As is known to those of skill in the art,various communication arrangements may be employed for communicationwith the hosts and with the data storage drives. In the example of FIG.3, host connections 80 and 81 are intended to be Ethernet and a SCSIbus, respectively, e.g., and may serve as host connections. However, bus82 comprises an example of a Fibre Channel bus which is a high speedserial data interface, allowing transmission over greater distances thanthe SCSI bus systems.

According to some approaches, the data storage drives 15 may be in closeproximity to the communication processor node 50, and may employ a shortdistance communication scheme, such as Ethernet, or a serial connection,such as RS-422. Thus the data storage drives 15 may be individuallycoupled to the communication processor node 50 by lines 70.Alternatively, the data storage drives 15 may be coupled to thecommunication processor node 50 through one or more networks.

Furthermore, additional storage frames 11 may be provided, whereby eachis preferably coupled to the adjacent storage frame. According tovarious approaches, any of the additional storage frames 11 may includecommunication processor nodes 50, storage slots 16, data storage drives15, networks 60, etc.

Moreover, as described above, the automated data storage library 10 maycomprise a plurality of accessors. A second accessor 28, for example, isshown in a right hand service bay 14 of FIG. 3. The second accessor 28may include a gripper assembly 30 for accessing the data storage media,and an XY system 255 for moving the second accessor 28. The secondaccessor 28 may run on the same horizontal mechanical path as the firstaccessor 18, and/or on an adjacent (e.g., separate) path. Moreover, theillustrative control system additionally includes an extension network200 which forms a network coupled to network 60 of the storage frame(s)11 and to network 157 of left hand service bay 13.

In FIG. 3 and the accompanying description, the first and secondaccessors are associated with the left hand service bay 13 and the righthand service bay 14 respectively. However, this is for illustrativepurposes and there may not be an actual association. Thus, according toanother approach, network 157 may not be associated with the left handservice bay 13 and network 200 may not be associated with the right handservice bay 14. Moreover, depending on the design of the library, it maynot be necessary to have a left hand service bay 13 and/or a right handservice bay 14 at all.

An automated data storage library 10 typically comprises one or morecontrollers to direct the operation of the automated data storagelibrary. Moreover, host computers and data storage drives typicallyinclude similar controllers. A library controller may take manydifferent forms and may comprise, for example, but is not limited to, anembedded system, a distributed control system, a personal computer, aworkstation, etc. The term “library controller” as used herein isintended in its broadest sense as a device that includes at least oneprocessor, and optionally further circuitry and/or logic, forcontrolling and/or providing at least some aspects of libraryoperations.

Referring now to FIG. 4, a typical controller 400 is shown with aprocessor 402, Random Access Memory (RAM) 403, nonvolatile memory 404,device specific circuits 401, and I/O interface 405. Alternatively, theRAM 403 and/or nonvolatile memory 404 may be contained in the processor402 as could the device specific circuits 401 and I/O interface 405. Theprocessor 402 may comprise, for example, an off-the-shelfmicroprocessor, custom processor, Field Programmable Gate Array (FPGA),Application Specific Integrated Circuit (ASIC), discrete logic, etc. TheRAM 403 is typically used to hold variable data, stack data, executableinstructions, etc.

According to various approaches, the nonvolatile memory 404 may compriseany type of nonvolatile memory such as, but not limited to, ElectricallyErasable Programmable Read Only Memory (EEPROM), flash Programmable ReadOnly Memory (PROM), battery backup RAM, hard disk drives, etc. However,the nonvolatile memory 404 is typically used to hold the executablefirmware and any nonvolatile data. Moreover, the I/O interface 405comprises a communication interface that allows the processor 402 tocommunicate with devices external to the controller. Examples maycomprise, but are not limited to, serial interfaces such as RS-232, USB(Universal Serial Bus) or Small Computer Systems Interface (SCSI). Thedevice specific circuits 401 provide additional hardware to enable thecontroller 400 to perform unique functions including, but not limitedto, motor control of a cartridge gripper. Moreover, the device specificcircuits 401 may include electronics that provide, by way of example butnot limitation, Pulse Width Modulation (PWM) control, Analog to DigitalConversion (ADC), Digital to Analog Conversion (DAC), etc. In addition,all or part of the device specific circuits 401 may reside outside thecontroller 400.

While the automated data storage library 10 is described as employing adistributed control system, the various approaches described and/orsuggested herein may be implemented in various automated data storagelibraries regardless of control configuration, including, but notlimited to, an automated data storage library having one or more librarycontrollers that are not distributed. Moreover, a library controller maycomprise one or more dedicated controllers of a library, depending onthe desired embodiment. For example, there may be a primary controllerand a backup controller. In addition, a library controller may compriseone or more processor nodes of a distributed control system. Accordingto one example, communication processor node 50 (e.g., of FIG. 3) maycomprise the library controller while the other processor nodes (ifpresent) may assist the library controller and/or may provide backup orredundant functionality. In another example, communication processornode 50 and work processor node 52 may work cooperatively to form thelibrary controller while the other processor nodes (if present) mayassist the library controller and/or may provide backup or redundantfunctionality. Still further, all of the processor nodes may comprisethe library controller. According to various approaches described and/orsuggested herein, a library controller may have a single processor orcontroller, or it may include multiple processors or controllers.

FIGS. 5A-5B illustrate the front 501 and rear 502 views of a datastorage drive 15, according to one embodiment. In the example depictedin FIGS. 5A-5B, the data storage drive 15 comprises a hot-swap drivecanister, which is in no way intended to limit the invention. In fact,any configuration of data storage drive may be used whether or not itincludes a hot-swap canister. As discussed above, a data storage drive15 is used to read and/or write data with respect to the data storagemedia, and may additionally communicate with a memory which is separatefrom the media, and is located within the cartridge. Thus, according toone approach, a data storage cartridge may be placed into the datastorage drive 15 at opening 503.

Furthermore, FIG. 6 illustrates an embodiment of a data storagecartridge 600 with a cartridge memory 610 shown in a cutaway portion ofthe Figure, which is in no way intended to limit the invention. In fact,any configuration of data storage cartridge may be used whether or notit comprises a cartridge memory. According to various approaches, mediaof the data storage cartridge media may include any type of media onwhich data may be stored, including but not limited to magnetic media,e.g., magnetic tape, disks, etc.; optical media, e.g., optical tape,disks, etc.; electronic media, e.g., PROM, EEPROM, flash PROM,CompactFlash™, Smartmedia™, Memory Stick™, etc.; etc., or other suitablemedia. Moreover, an example of a data storage cartridge that is widelyemployed in automated data storage libraries for mass data storage is amagnetic tape cartridge in which the media is magnetic tape.

Looking now to FIGS. 7A-7B, a multi-cartridge deep slot cell 100 havingbiasing springs 152 is depicted according to one embodiment. As shown inthe illustrative embodiment, the multi-cartridge deep slot cell 100comprises a housing 110 defining an interior space 115. Furthermore, aplurality of storage slots 120 is disposed within the housing, and maybe configured for storing up to a plurality of data storage cartridges600, depending on the desired approach. Alternatively, themulti-cartridge deep slot cell 100 may be built into the frame of theautomated data storage library according to one approach.

FIGS. 8A-8D illustrate an embodiment of a cartridge blocking mechanism150 having a retaining gate 660 that retains the data storage cartridgesin the multi-cartridge deep slot cell 100 according to one embodiment.As illustrated, according to one approach, the retaining gate 660 may beexternally attached to a multi-cartridge deep slot cell 100, relative toa front opening of the multi-cartridge deep slot cell 100, whereby theretaining gate 660 can be activated by an accessor 18, e.g., of anautomated tape library. Moreover, the retaining gate 660 allows forpositive cartridge retention against the pressure of biasing springs(see 152 of FIGS. 7A-7B), and ensures that one or more data storagecartridges do not get pushed out of the multi-cartridge deep slot cell100 simultaneously, while allowing the pushing mechanism (not shown) ofthe multi-cartridge deep slot cell 100 to continuously push data storagecartridge(s) to the opening in a multi-cartridge deep slot cell 100.Thus, according to one approach, the accessor 18 may open the retaininggate to gain access to the data storage cartridge in tier 1 and, uponits extraction, the biasing spring 152 moves the cartridge(s) positionedbehind the extracted cartridge forward, thereby promoting thecartridge(s) by one tier as will soon become apparent.

The basic working of the retaining gate is that the gate prevents thedata storage cartridge(s) from being pushed out of a multi-cartridgedeep slot cell 100. For example, as shown in FIGS. 8A-8D, a retaininggate 660 can be lifted by, for example, accessor 18 or by a frontstorage cartridge 642 for cartridge removal from/insertion into amulti-cartridge deep slot cell 100. Specifically, retaining gate 660 hasa pivoting arm 661 mounted on multi-cartridge deep slot cell 100 via apivoting post (not shown) that can be integral to a construction ofmulti-cartridge deep slot cell 100. Pivoting arm 661 is located below acatch 662 of retaining gate 660 whereby a thrust force TF through datastorage cartridge 644-642 caused by the pushing mechanism (not shown) ofmulti-cartridge deep slot cell 100 causes retaining gate 660 to stayclosed in a retaining position as shown in FIG. 8A. Moreover, theretaining gate 660 is preferably biased such that it closes in thedownward direction over the front opening of multi-cartridge deep slotcell 100. This constant biasing may be achieved via gravity as shown inFIG. 8A or by implementing a spring force, e.g., attached to retaininggate 660 (not shown).

For removal of front storage cartridge 642 by accessor 18 frommulti-cartridge deep slot cell 100, retaining gate 660 must be liftedupward to a releasing position whereby catch 662 of retaining gate 660is disengaged from front storage cartridge 642. This can be seen in FIG.8B where accessor 18 interfaces with retaining gate 660 by providing alifting force. Once retaining gate 660 is lifted to the releasingposition and accessor 18 is engaged with storage cartridge 642, accessor18 can pull storage cartridge 642 out of multi-cartridge deep slot cell100 and into accessor 18 without any interference of retaining gate 660as shown in FIG. 8C. In view of storage cartridges 644 and 643 beingstored in multi-cartridge deep slot cell 100, retaining gate 660 mustreturn to its retaining position to prevent storage cartridges 644 and643 from being ejected from multi-cartridge deep slot cell 100 by thethrust force TF of the pushing mechanism (not shown). During extractionof front storage cartridge 642 through the front opening ofmulti-cartridge deep slot cell 100, the retaining gate 660, which isbeing biased downward, moves back to the retaining position to engagestorage cartridge 643.

Once front storage cartridge 642 is extracted and storage cartridges 643and 644 are retained from being pushed out of multi-cartridge deep slotcell 100, retaining gate 660 has successfully completed its cartridgeretrieval process. Now retaining gate 660 demonstrates its ability towork for cartridge insertion into multi-cartridge deep slot cell 100.When accessor 18 begins to insert storage cartridge 642 back intomulti-cartridge deep slot cell 100, retaining gate 660 is lifted to itsreleasing position to allow storage cartridge 642 through the frontopening of multi-cartridge deep slot cell 100. Catch 662 of retaininggate 660 interfaces with a rear portion of storage cartridge 642, inparticular a beveled surface of catch 662 as shown in FIG. 8D, wherebyretaining gate 660 is lifted to its releasing position as shown in FIG.8B due to storage cartridge 642 being pushed in multi-cartridge deepslot cell 100 by accessor 18. In doing so, storage cartridges 644, 643are pushed deeper into multi-cartridge deep slot cell 100 by storagecartridge 642 in multi-cartridge deep slot cell 100 by accessor 18.Thus, the accessor is able to provide a force greater than the thrustforce TF antiparallel thereto, to overcome the directional biasing ofthe storage cartridges 644, 643. Upon full insertion intomulti-cartridge deep slot cell 100, retaining gate 660 moves to itsretaining position to engage storage cartridge 642 as shown in FIG. 8A.

Thus, looking to various embodiments presented herein, access to astorage slot may include the ability to remove a cartridge from astorage slot, the ability to place a cartridge into a storage slot, orcombinations thereof.

According to an exemplary embodiment, the storage slots from top tobottom are considered to be in parallel and comprise the same tier.Moreover, the storage slots from front to back, in a particular row, areconsidered to be in series and comprise sequential tiers.

Referring back to FIGS. 7A-7B, in accordance with one embodiment,storage slots 120 are depicted as being configured for storing up to aplurality of data storage cartridges 600, and arranged in sequentialorder of tiers 621, 622, 623, 624, 625 from front to rear. It should benoted that the frontmost tier 621 is also called “tier 1”, while thenext tier 622 is called “tier 2”, etc., and the last tier 625 is alsocalled the “rearmost” tier. However, referring to FIG. 2, in oneembodiment, the single cartridge storage slots 16 are also termed “tier0”.

Referring again to FIGS. 1-3, according to one embodiment, thecontroller of automated data storage library 10 may operate theaccessor(s) 18, 28 to selectively extract, place and/or transport datastorage cartridges with respect to the multi-cartridge deep slot cells100 and/or other elements of the automated data storage library 10. Forexample, the controller may facilitate extracting a cartridge from amulti-cartridge deep slot cell 100, transporting the cartridge to a datastorage drive 15 and placing the cartridge in the drive 15. Thecontroller may then extract the cartridge from the data storage drive15, while directing the accessor to transport the cartridge to aspecific multi-cartridge deep slot cell 100, and place the cartridgetherein.

In one embodiment, one or more data storage cartridges may be added intothe library, e.g., at an I/O station 24, 25, whereby the controller ofthe automated data storage library 10 may then operate the accessor(s)18, 28 to transport the cartridge(s) to specific multi-cartridge deepslot cell(s) 100, and place the cartridge(s) therein. Similarly, thecontroller may operate the accessor(s) to selectively extract, place andtransport data storage cartridges with respect to the single cartridgestorage slots 16, and/or transport inserted or added cartridge(s) tospecific single cartridge storage slots 16.

Now referring to FIG. 9, a storage system 900 is shown according to oneembodiment. Note that some of the elements shown in FIG. 9 may beimplemented as hardware and/or software, according to variousembodiments. In some approaches, the storage system 900 may beimplemented in an automated data storage library such as that shown inFIGS. 1-2. In other approaches, an automated data storage library suchas that shown in FIGS. 1-2 may be a tier of the storage system 900.

The storage system 900 may include a storage system manager 912 forcommunicating with a plurality of media on at least one higher storagetier 902 and at least one lower storage tier 906. The higher storagetier(s) 902 preferably may include one or more random access and/ordirect access media 904, such as hard disks in hard disk drives (HDDs),nonvolatile memory (NVM), solid state memory in solid state drives(SSDs), flash memory, SSD arrays, flash memory arrays, etc., and/orothers noted herein or known in the art. The lower storage tier(s) 906may preferably include one or more lower performing storage media 908,including sequential access media such as magnetic tape in tape drivesand/or optical media, slower accessing HDDs, slower accessing SSDs,etc., and/or others noted herein or known in the art. One or moreadditional storage tiers 916 may include any combination of storagememory media as desired by a designer of the system 900. Also, any ofthe higher storage tiers 902 and/or the lower storage tiers 906 mayinclude some combination of storage devices and/or storage media.

The storage system manager 912 may communicate with the storage media904, 908 on the higher storage tier(s) 902 and lower storage tier(s) 906through a network 910, such as a storage area network (SAN), as shown inFIG. 9, or some other suitable network type. The storage system manager912 may also communicate with one or more host systems (not shown)through a host interface 914, which may or may not be a part of thestorage system manager 912. The storage system manager 912 and/or anyother component of the storage system 900 may be implemented in hardwareand/or software, and may make use of a processor (not shown) forexecuting commands of a type known in the art, such as a centralprocessing unit (CPU), a field programmable gate array (FPGA), anapplication specific integrated circuit (ASIC), etc. Of course, anyarrangement of a storage system may be used, as will be apparent tothose of skill in the art upon reading the present description.

In more embodiments, the storage system 900 may include any number ofdata storage tiers, and may include the same or different storage memorymedia within each storage tier. For example, each data storage tier mayinclude the same type of storage memory media, such as HDDs, SSDs,sequential access media (tape in tape drives, optical disk in opticaldisk drives, etc.), direct access media (CD-ROM, DVD-ROM, etc.), or anycombination of media storage types. In one such configuration, a higherstorage tier 902, may include a majority of SSD storage media forstoring data in a higher performing storage environment, and remainingstorage tiers, including lower storage tier 906 and additional storagetiers 916 may include any combination of SSDs, HDDs, tape drives, etc.,for storing data in a lower performing storage environment. In this way,more frequently accessed data, data having a higher priority, dataneeding to be accessed more quickly, etc., may be stored to the higherstorage tier 902, while data not having one of these attributes may bestored to the additional storage tiers 916, including lower storage tier906. Of course, one of skill in the art, upon reading the presentdescriptions, may devise many other combinations of storage media typesto implement into different storage schemes, according to theembodiments presented herein.

According to some embodiments, the storage system (such as 900) mayinclude logic configured to receive a request to open a data set, logicconfigured to determine if the requested data set is stored to a lowerstorage tier 906 of a tiered data storage system 900 in multipleassociated portions, logic configured to move each associated portion ofthe requested data set to a higher storage tier 902 of the tiered datastorage system 900, and logic configured to assemble the requested dataset on the higher storage tier 902 of the tiered data storage system 900from the associated portions. Of course, this logic may be implementedas a method on any device and/or system or as a computer programproduct, according to various embodiments.

Automated data storage libraries use one or more robotic mechanisms tomove data storage cartridges back and forth from storage elements orimport/export elements to media drives located within the library. Whilethe precepts of the various embodiments of the present invention areapplicable to any type of data storage library, and should beinterpreted as such, much of the following description will describeembodiments in terms of an automated tape library. This is done by wayof example only and without limitation.

Automated tape libraries use one or more robotic mechanisms to move tapecartridges back and forth from storage elements or import exportelements to tape drives located within the tape library. Over a largepopulation of tape libraries, variations in component or manufacturingquality or bugs related to the library firmware of the robot may resultin the robot being unable to successfully handle the cartridges asdesired. Although the library may not have a failure, performing roboticError Recovery Processes (ERP's) downgrades the overall performance ofthe library. In some cases, it is difficult to diagnose the cause of therobotic cartridge handling issues. For example, if a robot position isincorrect when trying to grab a cartridge, it may be difficult todetermine if the robot is too high or too low or too far to the left orto the right. Robot position information may be vitally important fortrouble-shooting the tape library and determining a possible adjustmentto the underperforming robot.

In some cases where a tape library has repeated issues, a video of theerror would be helpful to help diagnose the root cause of the problem.If the tape library is deployed at a customer site, the field servicepersonnel may attempt to take a video using their smart phone andvarious video recording applications (apps) that may be nativelyembedded in the standard Operating System (OS) of the smart phone.However, it is expected to be difficult to properly diagnose theproblem, as field service personnel are inexperienced at capturingaccurate video and would be expected to generate a video of marginalvalue by not showing a particular video angle or proper location.

Field service personnel often carry a video capture device, i.e. asmartphone, on service visits to the customer's library. Variousembodiments described herein address the need for an apparatus on thelibrary for attaching a smart phone or other image capturing device tothe library components, such as the robotic accessor, in a manner thatorients the smart phone to record a video at the appropriate angle andto focus on the correct points of interest. The video captured will helpdiagnose problems with the tape library robotics.

Referring back to FIG. 2, a tape library 10 has a robotic accessor 18that has a gripper assembly 20 to move data storage cartridges tovarious locations within the tape library. According to one embodiment,FIGS. 10A and 10B show a magnified view of a robotic accessor 1018 withan additional bracket 1004 for mounting a mobile telephone 1006 to therobotic accessor 1018. The robotic accessor 1018 of FIGS. 10A and 10Bmay be, or be similar to, the robotic accessor 18 of FIG. 2 in someembodiments.

FIGS. 10A-10B depict an apparatus 1000, in accordance with oneembodiment. As an option, the present apparatus 1000 may be implementedin conjunction with features from any other embodiment listed herein,such as those described with reference to the other FIGS. Of course,however, such an apparatus 1000 and others presented herein may be usedin various applications and/or in permutations which may or may not bespecifically described in the illustrative embodiments listed herein.Further, the apparatus 1000 presented herein may be used in any desiredenvironment.

According to an exemplary embodiment, an apparatus 1000 includes anaccessor 1018 configured to transport data storage cartridges in alibrary environment and a bracket 1004 that may receive a wireless imagecapture device 1006, for example iPhone™, GoPro™, Samsung™ Galaxy, etc,therein. Moreover, the bracket 1004 may be positioned to orient thewireless image capture device 1006 to capture images while the accessor1018 is transporting data storage cartridges.

According to one embodiment, the apparatus 1000 includes a bracket 1004that may be fixedly coupled to the accessor 1018 in a manner that thebracket 1004 may be removed from the accessor 1018 without damaging theapparatus 1000, i.e. detachably attached. For example, the bracket 1004may be detachably attached to the accessor 1018 by being clipped to theaccessor 1018, or attached by existing screws 1012, 1014 (as shown inFIG. 10A) on the accessor 1018, or attached by new screw positions onthe accessor 1018, or snapped on, bolted on, taped on, etc.

In one embodiment of the apparatus 1000, the accessor 1018 includes agripper 1020, where the bracket 1004 may be positioned to enable captureof images of the gripper 1020. In one approach, the bracket 1004 may bepositioned to cause the wireless image capture device 1006 to move in avertical and a horizontal direction with the gripper 1020 to enablecapture of images of the gripper 1020 as the gripper 1020 moves in thevertical (Y) and a horizontal (X) direction to retrieve and grip,deliver and release, load and unload, etc. the data storage cartridge atthe storage slots 16 (in FIG. 2), multi-cartridge deep slot cells 100(in FIG. 2), data storage drives 15 (in FIG. 2), etc.

In another approach, the apparatus 1000 includes at least two grippers1020 and the bracket 1004 may be positioned to orient the wireless imagecapture device 1006 to capture images of at least two of the grippers1020.

In various embodiments, the bracket on the robotic accessor secures thewireless image capture device so that the camera of the wireless imagecapture device may be pointed at the grippers. From this position, videocan be recorded of various activities of the grippers, for example, howthe robotic accessor is grabbing the data storage cartridges; whetherthe robot is having a problem grabbing the data storage cartridges;whether the grippers are grabbing too high, too low, too far to theright, too far to the left; whether the robotic accessor is bouncing orvibrating; etc.

According to the embodiment of the apparatus 1000, the bracket 1004 maybe positioned to orient the wireless image capture device 1006 tocapture images of activity of the gripper 1020 performing work on atleast one of a plurality of storage slots (see storage slots 16 in FIG.2) in the library (see library 10 in FIG. 2). In some approaches, thewireless image capture device may capture images of activity of thegripper performing work on two storage slots, or on three storage slots,etc. In one approach, the bracket 1004 may be positioned to orient thewireless image capture device 1006 to capture images of activity of thegripper 1020 performing work on at least one of a plurality of tapedrives (see data storage drive 15 in FIG. 2) in the library (see library10 in FIG. 2). In other approaches, the wireless capture image devicemay capture images of activity of the gripper performing work on twodata storage drives, or on three data storage drives, or on four datastorage drives, etc.

In various embodiments, the bracket 1004 may be mounted so that thewireless image capture device 1006 has the control button 1016accessible to the field service personnel. In other embodiments, thecontrol button may not be accessible by the field service personnelafter the wireless image capture device is positioned in the bracket. Insuch case, the wireless capture device may be controlled remotely.

In various embodiments, the bracket is mounted on the robotic accessorin a position that may direct the camera of the wireless image capturedevice at the activity under study on the robotic accessor so that thecamera moves with the movements of the robotic accessor. In otherapproaches, the bracket is mounted on the robotic accessor so that thewireless image capture device may be positioned to capture imageslooking up at the grippers from the bottom of the accessor. In anotherapproach the bracket is mounted on the robotic accessor so that thewireless image capture device may be positioned to capture imageslooking down at the grippers from above the grippers.

With continued reference to FIG. 10A, in one embodiment of apparatus1000, the bracket 1004 may be positioned to hold the wireless imagecapture device 1006 without interfering with the movement of theaccessor 1018. Furthermore, the bracket 1004 may be positioned to holdthe wireless image capture device 1006 without interfering withoperations within the library (see library 10 in FIG. 2).

Looking to FIG. 10A, according to the embodiment of apparatus 1000 thebracket 1004 may be configured to allow detachable coupling of the imagecapture device 1006 thereto. Furthermore, the bracket 1004 may securelyhold the wireless image capture device 1006 so that the wireless imagecapture device 1006 may not move in the bracket 1004 while the accessor1018 is transporting data storage cartridges. For example, the imagecapture device 1006 may be snapped into place, secured by constrainingstraps (e.g., Velcro straps, rubber bands, etc.), secured by sidemembers that engage the sides and possibly the bottom of the imagecapture device, etc.

In some approaches, the bracket may be custom formed to fit a specificmodel of image capture device. In other approaches, the bracket may bedesigned to universally fit a generic type of image capture device suchas a mobile phone. In such case, the bracket may be oriented orpositionable to enable proper positioning of the camera of the imagecapture device.

The bracket 1004 may be formed using any conventional process. Forexample, the bracket 1004 may be formed from a 3D printer. In someapproaches, the bracket for mounting the wireless image capture devicemay be printed on a 3D printer whenever required, e.g. on demand. 3Dprinting allows the appropriate bracket to be printed and quicklyfabricated for different generations and manufacturers of wireless imagecapture devices. Thus, field service personnel may have a bracketfabricated that fits the wireless image capture device carried by thefield service personnel for failure investigations on site at customerlocations.

In various embodiments, the bracket may be formed of hard material, forexample wood, metal, plastic, etc.

In one embodiment of apparatus 1000, the image capture device 1006 maybe a mobile telephone. Looking to FIG. 10B, in the embodiment ofapparatus 1000, the bracket 1004 includes an aperture 1010 therethrough.Moreover, the aperture 1010 may be aligned with a camera 1008 of thetelephone 1006 when the telephone 1006 is mounted in the bracket 1004.Furthermore, in some approaches, the bracket may be strategicallylocated to position the camera lens of the mobile telephone such that itmay capture video of both of the dual grippers performing work on aspecific side of the library where areas of interest such as storageslots and data storage drives are located.

With continued reference to FIGS. 10A and 10B, the wireless imagecapture device 1006 may not be hard-wired to a power source because theimage capture device 1006 can capture images without an electricalconnection to any other component on the apparatus 1000.

FIG. 11 depicts a method 1100, in accordance with one embodiment. As anoption, the present method 1100 may be implemented in conjunction withfeatures from any other embodiment listed herein, such as thosedescribed with reference to the other FIGS. Of course, however, such amethod 1100 and others presented herein may be used in variousapplications and/or in permutations which may or may not be specificallydescribed in the illustrative embodiments listed herein. Further, themethod 1100 presented herein may be used in any desired environment.Moreover, more or less operations than those shown in other FIGS may beincluded in method 1100, according to various embodiments. It shouldalso be noted that any of the aforementioned features may be used in anyof the embodiments described in accordance with the various methods.

An exemplary method for mounting a smart phone to the robotic accessorof a data storage library is provided in detail below according to oneembodiment. In desired position on the robotic accessor, the smartphonemay record a video with the proper alignment and focus in order todiagnose problems with the data storage library robotics.

Method 1100, as illustrated in FIG. 11 may start with step 1102 whichinvolves mounting a wireless capture device to an accessor to captureimages of an operation in a data storage library. One approach of method1100 may involve mounting the bracket to the accessor where the accessormay be configured to transport data storage cartridges in a libraryenvironment. Moreover, the bracket may be configured to receive awireless image capture device therein. And furthermore, the bracket maybe mounted in a position to orient the wireless image capture device tocapture images while the accessor is transporting data storagecartridges.

In one approach of step 1102 of method 1100, the bracket may be fixedlycoupled to the accessor in a manner that the bracket may be removed fromthe accessor without damaging the apparatus, i.e. detachably attached.For example, the bracket may be detachably attached to the accessor bybeing clipped to the accessor, or attached by existing screws on theaccessor, or attached by new screw positions on the accessor, etc.Typically, the bracket would be detachably attached to the carriage ofthe grippers.

In another approach of step 1102 of method 1100, the accessor mayinclude a gripper, where the bracket may be positioned to enable captureof images of the gripper.

In step 1104, as shown in FIG. 11, the bracket is mounted where thebracket may be positioned to cause the wireless image capture device tomove in a vertical and a horizontal direction with the gripper to enablecapture of images of the gripper as the gripper moves in the verticaland a horizontal direction.

At the customer location, field service personnel may be requested bythe support center or development lab to use a smart phone to record avideo of the data storage library. A method described herein includes asequence of steps for the field service personnel to follow in order tocapture images of an operation in a data storage library which has abracket mounted on an accessor according to one embodiment.

FIG. 12 depicts a method 1200, in accordance with one embodiment. As anoption, the present method 1200 may be implemented in conjunction withfeatures from any other embodiment listed herein, such as thosedescribed with reference to the other FIGS. Of course, however, such amethod 1200 and others presented herein may be used in variousapplications and/or in permutations which may or may not be specificallydescribed in the illustrative embodiments listed herein. Further, themethod 1200 presented herein may be used in any desired environment.Moreover, more or less steps than those shown in other FIGS may beincluded in method 1200, according to various embodiments. It shouldalso be noted that any of the aforementioned features may be used in anyof the embodiments described in accordance with the various methods.

In one embodiment, method 1200 involves a step 1202, as illustrated inFIG. 12 that may include locating a bracket mounted in a position toorient a wireless image capture device on the accessor. Moreover, theaccessor may be configured to transport data storage cartridges in alibrary environment. Typically, the bracket would be detachably attachedto the carriage of the grippers on the accessor. Furthermore, thebracket may be configured to receive the wireless image capture devicetherein.

In step 1204, the field service personnel may mount the wireless imagecapture device into the bracket where an aperture of the bracket may bealigned with an aperture of the wireless image capture device. In someapproaches the wireless image capture device may be a mobile telephone.In other approaches, the field service personnel may mount the mobiletelephone upside down so that the camera of the telephone is alignedwith the aperture of the bracket.

In step 1206, the field service personnel may turn on the wireless imagecapture device, if not already running.

In step 1208, the field service personnel may start the recording ofimages of the operation being done by the robotic accessor in the datastorage library.

In step 1210, the field service personnel may start running the accessorwhile the wireless image capture device is recording images of theoperation such as moving the data storage cartridges in the data storagelibrary.

In optional step 1212, the field service personnel may zoom the imagecapture device to record magnified images of the operation.

In step 1214, the field service personnel may stop the accessor. Invarious approaches, the accessor may be stopped by the field servicepersonnel when the accessor completes the activity under study (i.e. theoperation).

In step 1216, the recording of the images of the operation may bestopped on the wireless image capture device.

In decision step 1218, if the operation is not complete, the fieldservice personnel returns to step 1208 and restarts recording on thewireless image capture device. If the operation is complete from step1218, then the field service personnel may continue to step 1220 wherethe field personnel may remove the wireless image capture device fromthe bracket on the accessor.

In step 1222 the field service personnel may view the recorded images ofoperation on the wireless image capture device.

In step 1224, the field service personnel may send the recorded imagesof the accessor activity of the operation under study via a wirelessapplication on the mobile telephone from the customer site where thedata storage library is located to the support center or developmentlab. Experts at the support center or development lab may study thevideo and propose recommendations on repair actions for the fieldservice personnel to perform on the robotics or automated data storagelibrary system.

While the foregoing method may be performed, e.g., by a technician,other embodiments may include methodology whereby some of the foregoingsteps are controlled electronically, by a remote user, etc.

Example 1: Controlled by Library and Field Service Personnel Remotely

In this example, the field service personnel may position and mount thewireless capture device on the accessor (steps 1202 and 1204). Using aremote controller, e.g. a laptop computer, tablet, iWatch paired to theiPhone on the accessor, library interface, etc, the field servicepersonnel turns on the wireless image capture device (step 1206) andstarts recording (step 1208). The Library is configured run the accessorand stop the accessor (steps 1210 and 1214). Then the field servicepersonnel, using a remote controller, may zoom the image capture deviceto record magnified images of the operation (step 1212), may stop therecording of the images (step 1216), or restart recording images if theoperation is not complete (step 1208). When the operation is complete(step 1218), the field service personnel removes the image capturedevice from the accessor (step 1220), and views the recorded images onthe wireless capture device (step 1222). Optionally, the field servicepersonnel may then upload the images to either the remote controller, orto the Support Center/Development Lab step 1224).

During step 1208, the video being captured during this time may beviewed simultaneously on the remote controller for the field servicepersonnel to view while the operation is taking place. The field servicepersonnel, using the remote controller, may zoom in at different timesor different locations during video capture (step 1212). Moreover, thefield service personnel may stop the video recording and restart thevideo recording at a different location or time (steps 1208, 1212,1216).

Example 2: Controlled by Library, Positioned by Field Service Personnel,and Controlled by Support Center/Development Lab Remotely

In this example, the field service personnel may position and mount thewireless capture device on the accessor (steps 1202 and 1204). The fieldservice personnel, using a remote controller, may connect the wirelesscapture device with wireless server so that the SupportCenter/Development Lab may remotely control the wireless capture deviceon the accessor. The Support Center/Development Lab may remotely turn onthe image capture device (step 1206) and start recording (step 1208).The Library Controller is configured to run the accessor and stop theaccessor (steps 1210 and 1214). The Support Center/Development Lab, viaremote controller, may zoom into selected images (step 1212), may stopthe recording of the images (step 1216), or restart recording the images(step 1208). When the Support Center/Development Lab is satisfied withimages (step 1218), the field service personnel may remove the imagecapture device from the accessor (step 1220), view the recorded imageson the wireless capture device (step 1222), and, optionally, send, usingwireless transfer, the image recordings, i.e. video, to the SupportCenter/Development Lab (step 1224).

Example 3: Positioned by the Field Service Personnel and Controlled bySupport Center/Development Lab Remotely

In this example, the field service personnel may position, mount thewireless capture device on the accessor, and turn on the wirelesscapture device (steps 1202 and 1204). The Support Center/Development Labconnects to the wireless capture device with wireless server so that theSupport Center/Development Lab may remotely control the wireless capturedevice on the accessor. The Support Center/Development Lab may remotelyturn on the image capture device (step 1206) and start recording (step1208). The Support Center/Development Lab configures the library, and byremote controller, runs the accessor (step 1210) and stops the accessor(step 1212). The Support Center/Development Lab, via remote controller,may zoom into selected images (step 1212), may stop the recording of theimages (step 1216), or restart recording the images (step 1208). Whenthe Support Center/Development Lab is satisfied with images (step 1218),the field service personnel may remove the image capture device from theaccessor (step 1220), view the recorded images on the wireless capturedevice (step 1222), and, optionally, send, using wireless transfer, theimage recordings, i.e. video, to the Support Center/Development Lab(step 1224).

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out steps of thepresent invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

Moreover, a system according to various embodiments may include aprocessor and logic integrated with and/or executable by the processor,the logic being configured to perform one or more of the process stepsrecited herein. By integrated with, what is meant is that the processorhas logic embedded therewith as hardware logic, such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), etc. By executable by the processor, what is meant is that thelogic is hardware logic; software logic such as firmware, part of anoperating system, part of an application program; etc., or somecombination of hardware and software logic that is accessible by theprocessor and configured to cause the processor to perform somefunctionality upon execution by the processor. Software logic may bestored on local and/or remote memory of any memory type, as known in theart. Any processor known in the art may be used, such as a softwareprocessor module and/or a hardware processor such as an ASIC, a FPGA, acentral processing unit (CPU), an integrated circuit (IC), a graphicsprocessing unit (GPU), etc.

A data processing system suitable for storing and/or executing programcode may include at least one processor, which may be or be part of acontroller, coupled directly or indirectly to memory elements through asystem bus, such as processor 400 of FIG. 4. The memory elements caninclude local memory employed during actual execution of the programcode, such as nonvolatile memory 404 of FIG. 4, bulk storage, and cachememories which provide temporary storage of at least some program codein order to reduce the number of times code must be retrieved from bulkstorage during execution.

It will be clear that the various features of the foregoing systemsand/or methodologies may be combined in any way, creating a plurality ofcombinations from the descriptions presented above.

It will be further appreciated that embodiments of the present inventionmay be provided in the form of a service deployed on behalf of acustomer to offer service on demand.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of an embodiment of the presentinvention should not be limited by any of the above-described exemplaryembodiments, but should be defined only in accordance with the followingclaims and their equivalents.

What is claimed is:
 1. A computer-implemented method for remotelycontrolling a capture of images of a data storage library duringoperation thereof, the computer-implemented method comprising: pairing aremote controller to a wireless image capture device that is coupled toa bracket mounted on an accessor; instructing the wireless image capturedevice to start recording images of the data storage library duringoperation thereof, including movement of the accessor; thereafter,instructing the wireless image capture device to stop recording imagesof the data storage library during operation thereof; and instructingthe wireless image capture device to save the recorded images to a file.2. The computer-implemented method as recited in claim 1, wherein theaccessor is configured to transport data storage cartridges in a libraryenvironment.
 3. The computer-implemented method as recited in claim 1,comprising instructing the wireless image capture device to zoom in torecord magnified images of the data storage library during operationthereof.
 4. The computer-implemented method as recited in claim 1,wherein the wireless image capture device is instructed to stoprecording when the accessor completes an operation.
 5. Thecomputer-implemented method as recited in claim 1, wherein the wirelessimage capture device is instructed to restart recording images afterstopping, wherein the wireless image capture device is instructed toagain stop recording when the accessor completes an operation.
 6. Thecomputer-implemented method as recited in claim 1, wherein the wirelessimage capture device is a mobile telephone.
 7. The computer-implementedmethod as recited in claim 1, comprising instructing the wireless imagecapture device to upload the file of recorded images to a computer. 8.The computer-implemented method as recited in claim 1, comprisinginstructing the wireless image capture device to send the file ofrecorded images to a support center.
 9. A computer-implemented methodfor remotely controlling, by a support center, a capture of images of adata storage library during operation thereof with a wireless imagecapture device located at a customer site, the computer-implementedmethod comprising: connecting to the wireless image capture device,wherein the wireless image capture device is configured to be controlledremotely by a remote controller located at the support center; sendingan instruction to the data storage library, by the remote controllerlocated at the support center, to move an accessor of the data storagelibrary; sending an instruction to the wireless image capture device, bythe remote controller, to start recording images of the data storagelibrary during operation thereof, wherein the wireless image capturedevice is mounted in a bracket on the accessor; sending an instructionto the data storage library, by the remote controller, to stop movingthe accessor; sending an instruction to the wireless image capturedevice, by the remote controller, to stop recording images of the datastorage library; and receiving the recorded images from the wirelessimage capture device.
 10. The computer-implemented method as recited inclaim 9, wherein the accessor is configured to transport data storagecartridges in a library environment.
 11. The computer-implemented methodas recited in claim 9, comprising sending an instruction to the wirelessimage capture device, by the remote controller, to zoom in to recordmagnified images of the data storage library during operation thereof.12. The computer-implemented method as recited in claim 9, wherein thewireless image capture device is instructed to stop recording when theaccessor completes an operation.
 13. The computer-implemented method asrecited in claim 9, wherein the accessor is stopped when the accessorcompletes an operation.
 14. The computer-implemented method as recitedin claim 9, wherein the wireless image capture device is instructed torestart recording images after stopping, wherein the wireless imagecapture device is instructed to again stop recording images when theaccessor completes an operation.
 15. The computer-implemented method asrecited in claim 9, comprising sending an instruction to the wirelessimage capture device, by the remote controller, to upload the recordedimages to a remote computer.
 16. The computer-implemented method asrecited in claim 9, further comprising sending a notification to a fieldrepresentative at the customer site to mount the wireless image capturedevice into the bracket on the accessor.
 17. The computer-implementedmethod as recited in claim 9, further comprising sending a notificationto a field representative at the customer site to remove the wirelessimage capture device from the bracket on the accessor.
 18. Thecomputer-implemented method as recited in claim 9, wherein the wirelessimage capture device is a mobile telephone.
 19. The computer-implementedmethod as recited in claim 18, further comprising, sending aninstruction to the mobile telephone, by the remote controller, to sendthe recorded images of accessor activity of the data storage library andoperation thereof via a wireless application on the mobile telephonefrom the customer site to the support center.